Skip to content

Release 0.3.5 with corrected shared lifecycle guidance - #7

Merged
TerminallyLazy merged 1 commit into
mainfrom
codex/public-plugin-guidance
Sep 8, 2026
Merged

Release 0.3.5 with corrected shared lifecycle guidance#7
TerminallyLazy merged 1 commit into
mainfrom
codex/public-plugin-guidance

Conversation

@TerminallyLazy

@TerminallyLazy TerminallyLazy commented Sep 8, 2026

Copy link
Copy Markdown
Owner

Correct shared skill and README guidance: current Codex public uploads also include native lifecycle hooks; older packages may omit them. Keep the native Claude hooks and runtime contract unchanged.

Validation: Claude package validation passed; runtime remains 0.15.7.

High-level PR Summary

This release bumps the version to 0.3.5 and corrects documentation guidance about lifecycle hooks. The changes clarify that current Codex public uploads include native lifecycle hooks, while older skills-only packages may omit them. All modifications are documentation updates to reflect the current state of the package, with version number updates across configuration files and validation scripts to maintain consistency.

⏱️ Estimated Review Time: 5-15 minutes

💡 Review Order Suggestion
Order File Path
1 skills/tree-ring-memory/SKILL.md
2 README.md
3 .claude-plugin/plugin.json
4 .claude-plugin/marketplace.json
5 SUBMISSION.md
6 scripts/validate.py

Need help? Join our Discord

@coderabbitai

coderabbitai Bot commented Sep 8, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: ed466c3e-1525-446c-a55f-074efc441f55


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Release 0.3.5 with corrected public lifecycle guidance

📝 Documentation ⚙️ Configuration changes 🧪 Tests 🕐 Less than 10 minutes

Grey Divider

AI Description

• Correct guidance to reflect native hooks in current public Codex packages.
• Release wrapper 0.3.5 while preserving Claude hooks and runtime 0.15.7.
• Synchronize manifests, submission metadata, and validation expectations.
Diagram

graph TD
  R["Release 0.3.5"] --> M["Plugin manifests"] --> V["Validation script"]
  R --> G["Lifecycle guidance"] --> RD["README"]
  G --> SK["Shared skill"]
  R --> SUB["Submission dossier"] --> V
Loading
High-Level Assessment

The current approach is appropriate: correct the two public guidance surfaces and synchronize every wrapper-version authority in the same release. A documentation-only edit without a version bump was considered but would leave published package metadata and validation expectations inconsistent.

Files changed (6) +9 / -10

Tests (1) +2 / -2
validate.pyValidate wrapper and submission version 0.3.5 +2/-2

Validate wrapper and submission version 0.3.5

• Updates the expected wrapper version and required submission marker so validation enforces the 0.3.5 release metadata.

scripts/validate.py

Documentation (3) +5 / -6
README.mdCorrect public package lifecycle-hook guidance +2/-3

Correct public package lifecycle-hook guidance

• Clarifies that older skills-only packages may omit automatic lifecycle hooks, while current Git and public upload packages include them. Retains the trust-flow and new-session requirements for newly configured Codex hooks.

README.md

SUBMISSION.mdUpdate submission dossier for release 0.3.5 +1/-1

Update submission dossier for release 0.3.5

• Changes the marketplace submission release reference from v0.3.4 to v0.3.5.

SUBMISSION.md

SKILL.mdClarify lifecycle hooks in current Codex packages +2/-2

Clarify lifecycle hooks in current Codex packages

• Replaces the blanket skills-only limitation with guidance that only older packages may omit hooks. Explicitly states that current Codex packages, including public uploads, provide automatic lifecycle hooks.

skills/tree-ring-memory/SKILL.md

Other (2) +2 / -2
marketplace.jsonBump marketplace wrapper version to 0.3.5 +1/-1

Bump marketplace wrapper version to 0.3.5

• Updates the marketplace release metadata to identify wrapper version 0.3.5.

.claude-plugin/marketplace.json

plugin.jsonBump plugin manifest version to 0.3.5 +1/-1

Bump plugin manifest version to 0.3.5

• Updates the authoritative plugin manifest version for the new wrapper release. Hook declarations and runtime behavior remain unchanged.

.claude-plugin/plugin.json

@TerminallyLazy
TerminallyLazy merged commit 0e55ec0 into main Sep 8, 2026
2 of 3 checks passed
@TerminallyLazy
TerminallyLazy deleted the codex/public-plugin-guidance branch September 8, 2026 20:50
@qodo-code-review

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 🔗 Cross-repo conflicts (1) 📜 Skill insights (0)

Grey Divider


Action required

1. Public uploads lack automatic hooks 🔗 Cross-repo conflict ≡ Correctness
Description
README.md and skills/tree-ring-memory/SKILL.md claim that current public Codex uploads include
automatic hooks, while Tree_Ring_Memory's public-upload builder removes the hooks manifest entry
and all /hooks/ files and TERMS.md still defines the separate OpenAI upload as skills-only.
Users who install that artifact or consult the terms will receive contradictory lifecycle guidance
and may expect automatic recall and checkpoints that still require separate CLI or project-hook
configuration.
Code

skills/tree-ring-memory/SKILL.md[35]

+   automatic hooks. Current Codex packages include them, including the public upload. Use `integrations status --verbose` to inspect the last
Evidence
The changed README and skill documentation explicitly claim that current public/Codex uploads
provide automatic hooks, but the canonical repository's builder removes the hook declaration,
excludes every hook file, and validates that the ZIP has no hook directory; the unchanged terms
likewise describe the separate OpenAI upload as skills-only. Together, these sources show that the
same distribution boundary is documented with mutually exclusive lifecycle behavior and that the
shipped artifact does not support the newly claimed automation.

README.md[204-206]
skills/tree-ring-memory/SKILL.md[34-36]
README.md[202-207]
skills/tree-ring-memory/SKILL.md[33-36]
TERMS.md[8-10]
External repo: TerminallyLazy/Tree_Ring_Memory, plugins/tree-ring-memory/packaging/build-codex-skills-only.py [1-3]
External repo: TerminallyLazy/Tree_Ring_Memory, scripts/validate-plugin-packages.py [263-270]
External repo: TerminallyLazy/Tree_Ring_Memory, scripts/validate-plugin-packages.py [287-294]
External repo: TerminallyLazy/Tree_Ring_Memory, README.md [109-115]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Correct the lifecycle guidance for the current Codex public-upload artifact. The README and skill currently say it includes automatic hooks, while the artifact remains skills-only and `TERMS.md` describes it that way.

## Issue Context
The canonical Tree_Ring_Memory builder removes the hook declaration and validates that no hook files enter the public ZIP, so automatic recall and checkpoints still require separate CLI or project-hook configuration. Either restore the skills-only warning in the README and skill, or coordinate and release the upstream package change before claiming public-upload hook support; then make the terms and all package descriptions consistently distinguish older packages from current Git and public-upload packages.

## Fix Focus Areas
- TERMS.md[8-10]
- README.md[202-207]
- skills/tree-ring-memory/SKILL.md[33-36]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


Grey Divider

Context sources
✅ Cross-repo context — repo relationships
  Explored: repo: TerminallyLazy/Tree_Ring_Memory (sha: 8319b40d)
  Explored: repo: TerminallyLazy/tree-ring-memory-agent-zero (sha: e8712174)
Review mode: ⚖️ Balanced: Although the diff is small, it changes runtime validation logic and release metadata alongside public lifecycle guidance, so a complete review is warranted.

Grey Divider

Tip of the day
💡 Did you know, you can tweak Display preferences with a live preview to see your comment before it ships

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Lifecycle hooks need CLI 0.15.6 or newer; a skills-only plugin package has no
automatic hooks. Use `integrations status --verbose` to inspect the last
Lifecycle hooks need CLI 0.15.6 or newer; older packages may omit
automatic hooks. Current Codex packages include them, including the public upload. Use `integrations status --verbose` to inspect the last

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Action required

1. Public uploads lack automatic hooks 🔗 Cross-repo conflict ≡ Correctness

README.md and skills/tree-ring-memory/SKILL.md claim that current public Codex uploads include
automatic hooks, while Tree_Ring_Memory's public-upload builder removes the hooks manifest entry
and all /hooks/ files and TERMS.md still defines the separate OpenAI upload as skills-only.
Users who install that artifact or consult the terms will receive contradictory lifecycle guidance
and may expect automatic recall and checkpoints that still require separate CLI or project-hook
configuration.
Agent Prompt
## Issue description
Correct the lifecycle guidance for the current Codex public-upload artifact. The README and skill currently say it includes automatic hooks, while the artifact remains skills-only and `TERMS.md` describes it that way.

## Issue Context
The canonical Tree_Ring_Memory builder removes the hook declaration and validates that no hook files enter the public ZIP, so automatic recall and checkpoints still require separate CLI or project-hook configuration. Either restore the skills-only warning in the README and skill, or coordinate and release the upstream package change before claiming public-upload hook support; then make the terms and all package descriptions consistently distinguish older packages from current Git and public-upload packages.

## Fix Focus Areas
- TERMS.md[8-10]
- README.md[202-207]
- skills/tree-ring-memory/SKILL.md[33-36]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant